Dev_Tasks	
The application program running in the PLC CPU controls the timing and content of each query by sending a COMMREQ message. The COMMREQ must be addressed to the CPU serial port that is connected to the Modbus RTU serial network. COMMREQ data specifies the content of the query. When the query/response transaction completes, a COMMREQ status value indicates the success or failure of the transaction. 
Reference: Modbus RTU Master Communications GFK-2220A
#END#

CR_Task
TASK input at Commreq function block
#END#

RTM_Task
The PLC selects which port a COM_REQ is addressed to through the TASK input to the function block. Selecting task 101 initializes port 1 and task 102 initializes port 2 on the RTM.
#END#

Wait_Flag	
This flag determines whether PLC will wait until the device serial ports receive the intended data before continuing. The request can either send a message and wait for a reply, or send a message and continue without waiting for a reply. If the Command Block specifies that the program will not wait for a reply, the Command Block contents are sent to the device and ladder program execution resumes immediately. This is referred to as NOWAIT mode. If the Command Block specifies that the program will wait for a reply, the Command Block contents are sent to the targeted device and the CPU waits for a reply for a maximum length of time specified in the Command Block. If the device does not respond in that time, ladder program execution resumes. This is referred to as WAIT mode.
#END#

Idle_Tmout	
The idle timeout value is the maximum time the PLC waits for the device to acknowledge receipt of the request. For NOWAIT, this value is not used. (Any timeout value is ignored; it can be zero.) If WAIT is selected, this word specifies the idle timeout period, in 100-microsecond increments.
#END# 

Max_Comm_Tm	
This word contains the maximum amount of time the program should hold the window open when the device is busy. For NOWAIT, this value is not used. (Any timeout value is ignored; it can be zero.) If WAIT is selected, this word specifies the maximum time in 100 microsecond increments.
#END#

Configure Ports
RTU is a half-duplex protocol. It is commonly wired in either of two configurations: 2-Wire or 4-Wire.The RTU protocol as implemented on the CMMs and CPUs provides for Slave operation only. However, a MegaBasic application file is available that enables a PCM module to support the RTU Master or Slave implementation. 1.Master - the initiating device in a Master/Slave system. 2.Slave - the responding device in a Master/Slave system. The RTU protocol can be enabled on none, one, or both of the serial ports of the CMM module, on several CPU serial ports, and on PCM serial ports (using the MegaBasic application file) using either the RS-232 or RS-422/RS-485 electrical standard. Essentially, any combination of protocols, ports, and electrical standards are available with one exception: The Series 90-30 CMM cannot support RS-422/RS-485 on port 1. Port selection, station address, data rates, flow control, and parity values can be configured.
#END#

Initialize RTU Master Port
Initialize RTU Master Port is a Local command. The standard Serial Port Setup COMMREQ may be used to configure the port for Modbus RTU Master operation using configuration values specified in the data block. It may also be used to modify configuration values during Modbus RTU Master operation. When the CPU hardware configuration assigns a different protocol to the target port and this COMMREQ is used to start Modbus RTU Master, the application must not issue additional Modbus RTU Master COMMREQs until this one completes successfully. The application must monitor the value in the COMMREQ status location do determine successful completion. When this COMMREQ is used to re-initialize Modbus RTU Master during operation, the Diagnostic Status Words are cleared.
#END#

Initialize RTU Slave Port
Initialize RTU Slave Port is a Local command. The standard Serial Port Setup COMMREQ may be used to configure the port for Modbus RTU operation using configuration values specified in the data block. It may also be used to modify configuration values during Modbus RTU operation. When the CPU hardware configuration assigns a different protocol to the target port and this COMMREQ is used to start Modbus RTU Master, the application must not issue additional Modbus RTU Master COMMREQs until this one completes successfully. The application must monitor the value in the COMMREQ status location do determine successful completion. When this COMMREQ is used to re-initialize Modbus RTU during operation, the Diagnostic Status Words are cleared.
#END#

Clear RTU Master Diagnostic
This Local command clears the Modbus RTU Master diagnostic status data maintained by the port. All data words defined in the Diagnostic Data Format section above are set to zero. This command returns an error code if the port has not been initialized for Modbus RTU Master; otherwise it returns one.
#END#

Read RTU Master Dignstic Stat
Read RTU Master Diagnostic Status Words: 08001 (1F41). Local command. This command copies the Modbus RTU Master diagnostic status data maintained by the port to a reference address specified in the command block. The data is useful for debugging Modbus RTU master applications during development and for monitoring the RTU network during normal operation.
#END#

Send RTU Rd Frce Preset Qry
Send RTU Read/Force/Preset Query: 08002 (1F42). Remote command. This command sends a Modbus RTU Master Read, Force, Preset, or Report Device Type query message as specified in the command/data block.
#END#

Send RTU Diagnostic Query
Remote command. This command sends one of the following Modbus RTU Master queries as specified in the command/data block: Loopback/Maintenance.
#END#

Protocol
Protocol-Modbus RTU; Constant = 3
#END#

Data_Rate
Data Rate: The highest valid rate depends on the specific Modbus RTU Master device. For example, 19,200 bits/second (bps) is the highest data rate supported Modbus RTU Master and Slave on IC693CPU363, IC200CPU001 and IC200CPU002. IC200CPU005 and IC200CPUE05 currently support 57,600 bps.
#END#

Parity
Parity: Note that when parity = ODD or EVEN, the character length used by Modbus RTU Master is 11 bits: one start bit, 8 data bits, one parity bit and one stop bit. There is no parity bit when parity = NONE, and the character length is 10 bits. The Modbus RTU standard recommends 11 bits in all cases.
#END#

Flow_Control
Flow Control: 2 = SOFTWARE is invalid; a Parameter Error (020Ch) is returned to the status location specified in the Initialize Port COMMREQ.
When 0 = HARDWARE is specified, the port asserts RTS and waits for CTS to become active before transmitting. If CTS does not become active within 2 seconds, a time-out error code is returned to the status location specified in the Send RTU Query COMMREQ. If CTS becomes active and then is de-asserted while the port is transmitting, up to 5 milliseconds may elapse before transmission stops. The maximum number of characters transmitted after CTS is de-asserted is proportional to the data rate. These values are in addition to the character that is being transmitted at the time CTS is de-asserted. Data Rate Max. Characters after CTS is De-asserted.
*****************************************************************************************************************************************************************************************************
Data Rate 	Max. Characters after CTS is De-asserted	Data Rate 	Max. Characters after CTS is De-asserted	
*****************************************************************************************************************************************************************************************************
1200			1				19200			10
2400			2				38400			20
4800			3				57600			29
9600			5				115200			58
#END#

Turn_Delay
SNP Turnaround Delay: This value is ignored. However, the specified value must be valid (0 - 255).
#END#

TmOut
Response message time-out-the specified value must be greater than the sum of the longest receive-to-transmit delay for all slaves plus the longest response message transmission time at the current data rate. LONG = 8 Seconds; MEDIUM = 2 Seconds; STANDARD = 500 Milliseconds; SHORT  =200 Milliseconds.
When a Send RTU Query COMMREQ specifies a broadcast query, COMMREQ_OK is returned to the COMMREQ status location when this time-out expires. When a Send RTU Query COMMREQ specifies a non-broadcast query, a RESPONSE_TIMEOUT error code is returned to the COMMREQ status location when this time-out expires before a complete response is received. Modbus RTU requires a time-out in all cases. The STANDARD timeout (500 milliseconds) is recommended by the Modbus RTU standard. The time-out begins after the port has transmitted the last character of the query and stops when the character-gap time-out (Word 19) expires after the last response character is received. If the response time-out expires before the end of the character-gap time-out, the port is checked for a response message. If one is detected (for example, because the response time-out expired after the response was received but before the character-gap time-out expired), the response is processed normally after the gap timeout expires. If no valid response is detected, a time-out error code is returned to the COMMREQ status location.
#END#

Interface
Port Interface - Port 1 = RS-232, Port 2 = RS-485. Not software configurable in VersaMax or IC693CPU363; However, the specified value must be valid (0 or 1). 
#END#

Duplex_Mode
Select the mode: 2 wire or 4 wire mode.
#END#

Charac_Gap_Tmout
Character-gap time-out in 100-microsecond units. Range 0 - 65,535 (0 to 6.5535 seconds). This is the time interval that defines the end of each received response message. It is measured from the end of the last received character. RTS is off and the transmitter is silent during this interval. If a new query is ready for transmission, RTS is asserted no earlier than the end of this interval. On RS-485 ports, the Send Data and RTS signals remain in the high-impedance state until at least the end of this interval.
Zero specifies the default, defined as 3.5 character times at the specified data rate, assuming 11 bits per character.
*****************************************************************************************************************************************************************************************************
Data Rate 	Default (100 -sec. units) 	Data Rate 	Default (100 -sec. units)
*****************************************************************************************************************************************************************************************************
1200		322			19200		21
2400		161			38400		10
4800		80			57600		7
9600		40			115200		3
Any specified value smaller than the default is replaced by the default. This value also performs the function of the Modbus RTU slave receive-to-transmit delay. If the required delay is greater than the default value at the current data rate, increase the specified value to required delay in 100-microsecond units. If the required delay is less than the default at the current data rate, no additional delay is necessary.
#END#

RTS_Drop_Delay
RTS Drop Delay in 100 microsecond units: This is the time from the end the last transmitted character to the time when RTS is turned off (dropped). The receiver is disabled during transmission and remains disabled during the RTS drop delay time. If the specified delay is longer than the Modbus RTU slaves silent interval between the query and its response, the master will ignore all or part of the response. Zero specifies the default, defined as one character time at the specified data rate, assuming 11 bits per character. 
Data Rate 	Default (100 -sec. units) 	Data Rate 	Default (100 -sec. units)
1200		92			19200		6
2400		46			38400		3
4800		23			57600		2
9600		12			115200		1
Any specified value smaller than the default is replaced by the default. Note that RTS Drop Delay is specified in 10 millisecond units for Modbus RTU slave.
#END#

First_Diag_Word_To_Read
First Diagnostic Status Word to Read: The word number in the Diagnostic Status data where the data that will be read begins. To read all of the data, specify 1 here and 38 in the next parameter. The total of the values in this parameter and next parameter must not be greater than the size of the Diagnostic Status Words in words plus one (39).
#END#

No_Diag_Word_To_Read
Number of Diagnostic Status Words to Read: The total count of Diagnostic Status data words that will be read. To read one word, specify 1. To read all of the data, specify 38 here and 1 in previous parameter. The total of the values in this parameter and previous parameter must not be greater than the size of the Diagnostic Status Words in words plus one (39).
#END#

Data_Memory_Type
Data Memory Type: The memory type where diagnostic status data will be returned. Format of Diagnostic Status Words:
**************************************************************************************************************************************************************************************************
Location 		Description
*******************************************************************************************************************************************************************************************************
Word 1 		RTU error status word: the LSB and MSB contain the Major and Minor error code values, respectively, from the most recent RTU Master
		COMMREQ error, internal error, or RTU exception response. Contains zero if no errors have occurred.
Word 2 		Number of RTU Master COMMREQs received from the PLC CPU. 
Word 3 		Number of RTU queries sent from the serial port.
Word 4 		Number of RTU queries that were not transmitted before the time-out expired.
Word 5 		Number of RTU normal responses received on the serial port.
Word 6 		Number of RTU exception (error) responses received on the serial port.
Word 7 		Number of RTU response time-outs.
Word 8 		Number of RTU responses with serial port errors.
Word 9 		Number of RTU responses with invalid length.
Word 10 		Number of RTU responses with invalid CRC.
Word 11 		Number of RTU responses with invalid device address.
Word 12 		Number of RTU responses with invalid function code.
Word 13 		Number of RTU Loopback/Maintenance responses with invalid data.
Word 14 		Number of RTU valid responses detected after response time-out
Word 15 - 18 	Last RTU query: the first 8 bytes of the most recent RTU query sent from the serial port. For queries shorter than 8 bytes, the extra bytes are undefined. 		Contains zeros if no queries have been sent.
Word 19 - 22 	Last RTU response: the first 8 bytes of the most recent RTU response received on the serial port. For responses shorter than 8 bytes, the extra bytes are 		undefined. Contains zeros if no responses have been received.
Word 23 - 38 	Error COMMREQ data block: a copy of the command/data block of the most recent COMMREQ that produced an error. Contains zeros if no COMMREQ 		errors have occurred. If the command/data block is longer than 16 words, only the first 16 words are copied.
#END#

Data_Address
Data Address: The one-based offset of the first word where diagnostic status data will be returned; for example, specify 101 for %R00101. Format of Diagnostic Status Words:
**************************************************************************************************************************************************************************************************
Location 		Description
*******************************************************************************************************************************************************************************************************
Word 1 		RTU error status word: the LSB and MSB contain the Major and Minor error code values, respectively, from the most recent RTU Master
		COMMREQ error, internal error, or RTU exception response. Contains zero if no errors have occurred.
Word 2 		Number of RTU Master COMMREQs received from the PLC CPU. 
Word 3 		Number of RTU queries sent from the serial port.
Word 4 		Number of RTU queries that were not transmitted before the time-out expired.
Word 5 		Number of RTU normal responses received on the serial port.
Word 6 		Number of RTU exception (error) responses received on the serial port.
Word 7 		Number of RTU response time-outs.
Word 8 		Number of RTU responses with serial port errors.
Word 9 		Number of RTU responses with invalid length.
Word 10 		Number of RTU responses with invalid CRC.
Word 11 		Number of RTU responses with invalid device address.
Word 12 		Number of RTU responses with invalid function code.
Word 13 		Number of RTU Loopback/Maintenance responses with invalid data.
Word 14 		Number of RTU valid responses detected after response time-out
Word 15 - 18 	Last RTU query: the first 8 bytes of the most recent RTU query sent from the serial port. For queries shorter than 8 bytes, the extra bytes are undefined. 		Contains zeros if no queries have been sent.
Word 19 - 22 	Last RTU response: the first 8 bytes of the most recent RTU response received on the serial port. For responses shorter than 8 bytes, the extra bytes are 		undefined. Contains zeros if no responses have been received.
Word 23 - 38 	Error COMMREQ data block: a copy of the command/data block of the most recent COMMREQ that produced an error. Contains zeros if no COMMREQ 		errors have occurred. If the command/data block is longer than 16 words, only the first 16 words are copied.
#END#

Target_RTU_Device_Add
Target RTU Device Address: This is the 8-bit address of the Modbus RTU slave to which the query is addressed, using Modbus addressing. Address zero is the broadcast address. Any query sent to the broadcast address should not result in a response. Valid device addresses are in the range 1 through 247 inclusive. Schneider/Modicon has reserved the values 248 to 255.
#END#

RTU_Function_Code
RTU Function Code: This is the 8-bit function code for the query. Only Force Single Output %Q, Preset Single Register %R, Force Multiple Outputs %Q and Preset Multiple Registers %R are valid for broadcast query.
#END#

RTU_Data_Start_Address
RTU Data Address/Start Address: The one-based offset into the target reference data type on the slave that specifies: 
1. The data location for the Force Single Output and Preset Single Register function codes;
2. The start of the data range for Read Output Table, Read Input Table, Read Registers, Read Analog Inputs, Force Multiple Outputs and Preset Multiple Registers function
codes; and
3. The starting byte number for the Read Scratch Pad Memory function code.
For example, specify 101 for either %R00101 in a GE Fanuc PLC or Holding Register 4101/40101 in a Schneider/Modicon PLC. This word is ignored for the Read Exception Status and Report Device Type function codes.
#END#

RTU_No_of_Points_Registers
RTU Number of Points/Registers/Byte: The number of 1-bit points (Read Output Table, Read Input Table, Force Multiple Outputs) or 16-bit registers (Read Registers, Read Analog Inputs, Preset Multiple Registers) that will be sent to the slave in a Force/Preset Multiple query or requested from the slave in a Read query, or the number of bytes that will be requested in a Read Scratch Pad Memory request. This word is ignored for the Force Single Output, Preset Single Register, Read Exception Status and Report Device Type function codes. Note that the Byte Count field in Force/Preset Multiple queries will be calculated from RTU Number of Points/Registers according to the size of the target reference type associated with the RTU Function Code.
#END#

Source_Data_Memory_Type
Data Memory Type: This is the memory reference data type in the local PLC for the source of transmitted data in Force/Preset queries or the destination where response data is copied for Read queries.
#END#
Source_Data_Address
Data Address: This is the one-based offset in the local PLC of the source data address for Force/Preset queries or the destination data address for Read queries. For
example, specify 101 for %R00101. The entire range of data references defined by the Data Memory Type, Data Address, and Number of Points/Registers/Bytes must be valid in the local PLC. For example, if the local PLC is configured with a Register Memory size of 2048 words, and the Number of Registers in a Read Registers query is 120, then the largest valid Data Address is %R01929 (2048 - 120 + 1).
#END#

Loopbk_Mntnce_Diag_Code
Loopback/Maintenance Diagnostic Code for Loopback/Maintenance queries.
Return Query Data:			target slave should respond by sending a duplicate of the query message. Not Valid as Broadcast Query
Initiate Communication Restart  		target slave(s) disable Listen-only Mode (if enabled). Valid as Broadcast Query
Force Listen-only Mode  			target slave(s) enable Listen-only Mode Valid as Broadcast Query
#END#

Loopbk_Mntnce_Data
Loopback/Maintenance Data: VALID VALUES DEPENDS ON PREVIOUS PARAMETER "Loopbk/Mntnce_Diag_Code". The following data values are required in Loopback/Maintenance queries; all others are invalid.
Diagnostic Code Value 	Loopback/Maintenance Data Value
0 			Any 16-bit unsigned value: 0 - 65,535 (0 - 0FFFFh)
1 			Clear Communications Event Log: 65280 (FF00h)
			Do not clear Event Log: 0 (0000h)
4 			0
#END#

Port_Mode
Select the port of the mode.
#END#

Dev_ID_RTU
Device_ID_RTU: This is the 8-bit address of the Modbus RTU slave to which the query is addressed, using Modbus addressing. Address zero is the broadcast address. Any query sent to the broadcast address should not result in a response. Valid device addresses are in the range 1 through 247 inclusive. Schneider/Modicon has reserved the values 248 to 255.
#END#

Receive_To_Transmit_Delay	
RTU slave receive-to-transmit delay. If the required delay is greater than the default value at the current data rate, increase the specified value to required delay in 100-microsecond units. If the required delay is less than the default at the current data rate, no additional delay is necessary.
#END#

RTS_Drop_Delay_10
RTS Drop Delay in 10 millisecond units: This is the time from the end the last transmitted character to the time when RTS is turned off (dropped). The receiver is disabled during transmission and remains disabled during the RTS drop delay time. If the specified delay is longer than the Modbus RTU slaves silent interval between the query and its response, the master will ignore all or part of the response. Zero specifies the default, defined as one character time at the specified data rate, assuming 11 bits per character. 
Data Rate 	Default (10 m-sec. units) 	Data Rate 	Default (10 m-sec. units)
1200		92			19200		6
2400		46			38400		3
4800		23			57600		2
9600		12			115200		1
Any specified value smaller than the default is replaced by the default. Note that RTS Drop Delay is specified in 10 millisecond units for Modbus RTU slave.
#END#


Initialize RTM
Slave Control Blocks (SCBs): A Slave Control Block (SCB) is a group of 15 words, which must be configured (with the exception of answer mode) for each slave RTU to be accessed. These SCBs are all stored together in a contiguous space of Series 90-30 PLC reference data words, which may be %R, %AI or %AQ. Each SCB provides such information as the slave RTU ID, delay between updates (seconds) and the call string (if dial out mode). The number of SCBs or stations accessible is limited to 32. The station ID is the ID, which is placed in the RTU message. A slave RTU with that ID is expected to respond. The update delay specifies the amount of time the RTM allows to pass between accesses to this particular slave station. Since each slave has its own update delay entry, priorities can be established. The dial string is used when a telephone modem is attached. This specifies the telephone number and control characters used for dialing. The status_indicator, mcb_index and number_of_retries may be accessed during operation and are reset during initialization.
Address 		Description 				Address 		Description
address 		Status Indicator 				address + 8 	Dial String Characters 5 & 6
address + 1 	Failed MCB Index 				address + 9 	Dial String Characters 7& 8
address + 2 	Number of Retries 				address + 10 	Dial String Characters 9 & 10
address + 3 	Station ID 				address + 11 	Dial String Characters 11 & 12
address + 4 	Update Delay 				address + 12 	Dial String Characters 13 & 14
address + 5 	Dial String 				address + 13 	Dial String Characters 15 & 16
address + 6 	Dial String Characters 1 & 2 			address + 14 	Dial String Characters 17 & 18
address + 7 	Dial String Character 3 & 4
The least significant byte in word 6 is the 1st digit to be dialed. The most significant byte in word 6 is the next. This storage pattern continues up to word 11. Digits are entered as a ANSII hexadecimal digit (i.e., 6 is entered as a 0x36)

Message Control Blocks (MCBs)
A Message Control Block (MCB) is a group of 6 words, which must be configured for each RTU command which is sent. These MCBs are all stored together in a contiguous space of 90-30 PLC reference data words, which may be %R, %AI or %AQ. Each MCB specifies the associated slave RTU ID, the RTU command, RTU data offset, RTU data length, and the type and offset of the PLC reference data which is accessed. The number of MCBs is limited to 1024.
Address 		Description  				Address 		Description  
address 		Station ID
address + 1 	RTU Command				address + 4 	PLC Reference Type
address + 2 	RTU Reference Offset			address + 5 	PLC Reference Offset
address + 3 	RTU Reference Length
The station ID is used to determine which slave is associated with this command. If multiple MCBs are defined for a particular ID, they are executed in the order encountered and do not need to be grouped together. All the commands for a currently selected slave are sent before accessing the next slave. The RTU command specifies the Modbus type command the slave should respond to. The following commands (word values) are supported:
Decimal 	Value 	Description 				Decimal 	Value 		Description
1 		Read Coil Status 				6 			Preset Single Holding Register
2 		Read Input Status 				7 			Read Exception Status
3 		Read Holding Register 			15 			Force Multiple Coils
4 		Read Input Register 			16 			Preset Multiple Holding Registers
5 		Force Single Coil 				65 			Return Slave ID
Any other command generates an error. The RTU reference offset specifies the starting data address on the slave RTU to access. The RTU reference length specifies the number of data items on the slave RTU to access. The PLC reference type specifies the local data reference table type where data on the PLC is accessed. The following types (word values) are supported: Table below - Supported PLC Reference Types and Offset Ranges:
Decimal Value 	Description 				Decimal Value 		Description
70 		%I 					8 			%R
72 		%Q 					10 			%AI
74 		%T 					12 			%AQ
76 		%M
Any other type value generates an error. The PLC reference offset specifies the local data reference table offset where the data on the PLC is accessed. Specifying an offset, which exceeds the reference data table size, generates an error.

Initialization Communications Request (COM_REQ):
Once the SCB and MCB lists are initialized, the starting address of each list along with other initialization parameters are passed to the RTM through a COM_REQ. Each of the communication ports requires its own set of lists and associated COM_REQ. The PLC selects which port a COM_REQ is addressed to through the TASK input to the function block. Since the RTM is slower to power up than the PLC, a delay of 5 seconds should be implemented in the ladder code before the COM_REQ is called. Additionally, the PLC should set the provided status reference to zero before making the call.
#END#

RTM_Mode
a. Direct (1) mode provides RS232 direct communication between the RTM and a single slave RTU. RTS is driven high during transmission to activate any external device. CTS is ignored. Although not typical in this mode, multiple stations can be scanned through a multi-drop line converter device. 
b. Multidrop (2) mode provides RS485 communications between the RTM and multiple slave RTUs. This mode active the RTM RS-485 drivers on the communications port. The transmission driver is only active while sending commands. 
c. Radio modem (3) mode provides RS232 communications to an external radio modem. RTS is asserted when the RTM has a message to transmit. The RTM then samples the CTS line which should be asserted by the radio modem when the transmitter has come up to power. A configurable radio modem time-out-timer is provided that releases the RTS line after a timeout with no CTS response and immediately issues a Modem-did-not-respond error. The receive line is monitored immediately after a send and does not depend on DCD.
d. Originate (4) mode provides RS232 communications to an external modem which may be used to originate calls to remote slaves. An entry is provided in the SCB for the user to provide a packed string of ANSII hexadecimal represented numbers and standard ATDT control characters. The RTM issues the call string and wait for a modem response. The modem must be compatible with verbal extended ATV0X4 commands. Once the connection is made, the MCB is processed as normal. When all messages for that station is complete, the connection is broken. 
e. Answer (5) mode provides RS232 communications to an external modem which may be used to answer calls placed by the remote slaves (compatible only with HE693RTU9x0). Once a call is received, the RTM issues a command to determine the station ID of the calling slave. Then the messages for that station is issued. Once all the messages for that station are complete, the connection is broken.
#END#

No_Of_SCBs
Specifies the number of Slave Control Blocks
#END#

SCB_Pointer_Type
Select the Slave Control Blocks memory type for identifying its location.
#END#

SCB_Pointer_Offset
Provide the Slave Control Blocks memory Offset for identifying its location. The offset is zero based. For example for using %R100 use 99 in this parameter.
#END#

No_Of_MCBs
Specifies the number of Master Control Blocks.
#END#

MCB_Pointer_Type
Select the Master Control Blocks memory type for identifying its location.
#END#

MCB_Pointer_Offset
Provide the Master Control Blocks memory Offset for identifying its location. The offset is zero based. For example for using %R100 use 99 in this parameter.
#END#

Port_Baud_Rate
Specifies the baud rate of the associated RTM port.
#END#

Port_Parameter_Word
Specifies the frame protocol:
Bit No.	Name		Interpretation
1 	Stop bits		0 means one stop bit; 1 means two stop bits
2-3 	Parity		00 means NO PARITY; 01 means EVEN PARITY; 10 means NO PARITY; 11 means ODD PARITY;
4 	Data bits		0 means seven data bits (ASCII); 1 means eight data bits (RTU).
5 	Interactive bit	0 means Interactive bit NOT SET; 1 means Interactive bit SET
6-16	Not Used		Reserved should be zero
#END#

Modem_Turnaround_Time
Specifies the amount of time in milliseconds (i.e. 2000=2sec) that the master waits for a response from the slave before recording a timeout error. Setting this value to zero defaults to 2.5 Sec.
#END#

Radio_CTS_Delay_Time
Radio modem mode only. Specifies the amount of time in milliseconds (i.e. 100=100mS) that the master waits for CTS (transmitter ready) after asserting RTS. Setting this value to zero defaults to 250mSec.
#END#
